I'd make the variables uppercase, this is a common practice in shell scripts. For the variables I would do:

DISTRIBUTION="alpine" # "alpine", "other", "another"
COMPONENT="edge" # "edge", "other", "another"

The benefit is the script will work when copied, and it should be obvious what the options are.

Also, it'd be nice if we could syntax-highlight these instructions as bash, but doesn't have to be this PR.

Can you remove the two # please select one: lines and the empty line between vars? It's obvious enough imho. I you want, you can add one of: a, b, c on the remaining comments.

remaining comments?

what exactly do you propose, sorry dont get it rigt now :/

@silverwind you might wana re-review as some bits changed:

• tryed syntax highliting - did not work (reverted)
• fixed intendation
• removed and added translation

-> screenshots updated to current pull state

Looks ok, I would add a empty line after the COMPONENT line, just to visually distinguish variables from commands.

Looks ok, I would add a empty line after the COMPONENT line, just to visually distinguish variables from commands.

Maybe it's even better to generate the texts from backend (Golang):

• It's easier to maintain than template (the template syntax is hard to read when the logic is complex or we need some special formats)
• It can add some tests to see what we want for various cases.